large files, on a suzeage-based model you can actually end up with pretty high costs. if they go to that direction for the public market. and just to kind of point out the problem with commercial usage, as mayor lee mentioned, there was an earthquake back east last month. 5.8. it didn't cause a lot of damage. but it caused a lot of -- a lot of interest and a lot of excitement on the east coast because they're not -- not necessarily used to those types of things. so as part of that, when that earthquake occurred, fema put out an advisory and the advisory stated, the key part is that due to overload of cell phone usage, there are reports of cell phone congestion. and fema was asking people to not use their phones, to use texting or other things to allow folks with legitimate problems to get into call 911.

and that just kind of plays up the fact of the problems that we have relying on a commercial service for our public safety usage. so bay web would solve a lot of those problems. this is a high-speed data network on the 4-g l.t.e. platform, cutting-edge technology. i'm sure you have seen the commercial. 4-g is the big thing now in commercial wireless technology. it's fast, it's faster than -- than 3-g technology. but the key -- there are several keys that are important for public safety and emergency response. one is, will achieve true inner operability region wide. whether he have one network that will cover the entire ten county bay area. so the devices we purchased in

san francisco we know will always work in santa clara county or up north in sonoma or napa county. oakland folks can come and, you know, mutual aid requirements and come to assist here in san francisco, their devices on this network will work because it's all the same network. one network region wide. it's also private. it's not shared with commercial traffic. that gets back to the concern that fema had about network congestion. we won't have the problem of network congestion on this network unless we have so many public safety users that we're -- you know, but that would be a good thing. we would hope that we have a lot of users on the network. but we won't have to share it with commercial users. in a large event or in an emergency, everybody gets on their cell phone these days. everybody wants to contact relatives, loved ones, find out if they're ok. in many cases they're taking pictures and sharing photos and

videos and really, you know, using up the commercial space. and the key with bay web is we wouldn't have to worry about sharing the network with commercial users. it's controlled. the technology, 4-g l.g.e. technology allows you to prioritize data transmissions. so, for example, if you have a command -- if you have an incident out on the field and you need to set up a command post, you can allocate more bandwidth to that commander in the field to allow that commander to view several different videos and send videos to certain staff out in the field and then throttle back on some of the other uses of the network to allow that capability. you can also prioritize by application. if you need to stream a lot of video, different videos, you can open up more bandwidth for the video and throttle back some other uses of the network or even by event. if you have a major event in one part of the city, you can

dedicate more bandwidth to that particular event and the needs of those first responders and throttle back on some of the other uses of the network. so it's very -- it's very controllable. it's also secure, dedicated to public safety, federal law requires or limits the use of this network to eligible users, which are public safety first responder users. and so we can adopt the incryption or security measures that we need to keep it a secure, dedicated network. a lot of new applications we're expecting to see on this, the really good ones are photos and video, ability to blast out an amber alert photo from the field to literally every public law enforcement officer in the region at the same time, almost realtime. the ability to -- to stream live video from from an incident or event to allow other first responders or law enforcement officials, to see what's going

on in other locations. and then the f.b.i. i know is setting -- is testing and developing some pretty cool applications where you can use like an iphone-type device to basically do fingerprinting in the field, shoot the fingerprint back and compare it with a database so you have fingerprints right there, right there in the field. a lot of this is under development but this is -- these are the capabilities we expect to see once we get network up and running. one important point have i to mention, this network did not support mission critical voice communications at this time sofment we're not replacing our land mobile radio. we're enhancing it with another system. there are efforts to develop mission critical voice capability on the l.t.e. platform, but we're not there yet and we're really in the early stages. we expect that to be several years before that's available but we're moving in that

direction. you can use it for voice. those of you who are familiar with voice-over i.p. or skype, those applications can be used on the network but your push to talk, channelized public safety radio functions are just not there yet. i wanted to make it clear that is one area we're not talking about replacing land mobile radios but enhancing them. i'm not going to spend a lot of time on this slide. it's awful hard to read. i apologize for it. there are several building blocks we needed to get to where we can build this data network. first we needed spectrum. we received through a waiver through the f.c.c. some 700 mega hertz spectrum that was actually freed up as part of the digital tv transition a few years ago and was dedicated by congress specifically for public safety broadband uses. san francisco, oakland and san

owe day applied to the f.c.c. to begin work building on this spectrum early and we received that waiver last year. funding and regional collaboration are two more pieces to it. i mentioned motorola got a $50 million grant under the broadband technology opportunities program and they're also contributing a match of $21 million to build the network. regional collaboration, you can cannot build the network without sites to put your radio so we have to have regions contribute to locations, to sites, the space to put radio transmitters out there to build a network. finally, governance, i mentioned the bay area authority and joint power authority, that had to be in place to govern everything. now, the only other thing i will say about this is we started with the spectrum and we got the

funding and getting regional collaboration and governance. we probably did it backwards, started with the governance and worried about the other pieces. but you use the hand you're dealt. so we had an opportunity to get the spectrum. funding became available and now we're building around that. they established a regional team, negotiating team to work with motorola to develop what we call the boom agreement. the beam agreement is a build, own, operate and maintain agreement whereby motorola would build, own, maintain the system for ten years and at that point transfer the entire system over to the authority at no cost. they tentatively agreed to play all of the site remediation cost, all of the cost of

installing equipment to make radio sites ready. they would then charge a service for operating on the network and we're tentatively looking at $38 a month peruser for the first year and after first year an adjustable rate that would never be more affordable than a market rate. a market rate is something that the authority and motorola would determine mutually but there's a condition in the ora grant that requires motorola to provide the service at a more affordable rate than market rate for the entire ten years. we would always get a better rate than the market rate. the key is finding market rate and we have probably some challenges with that. we have some guarantees the price will stay low for the entire ten-year agreement. there are no minimum user requirements. motorola was asking them to commit to a certain number of

users to load the system, guarantee a certain amount of revenues for operating. but we couldn't agree to that. so motorola has now backed off. there's no requirement that any jurisdiction have a minimum number of users. you can use it. you don't have to use it but we hope it's a valuable enough system that we will get lots of users. who pays for it? i talked a little bit about this, but the capital cost of the buildout, 100% paid by motorola. it should be motorola or the b-top grant. site remediation, motorola's covering those costs. site maintenance and upkeep, site owners and jurisdictions that own and control sites will have to put some resources into contributing the sites to staff time, to escorting motorola onto the sites to do the work. there will be in some cases these sites are leased and may

be lease modifications that will be some costs and utility, the electricity, whatever increases electricity on the sites to add the new equipment will be the responsibility of the jurisdictions. operations costs, motorola is responsible for operating the system. they will generate revenues through their monthly user fees to cover the cost of operation. but, again, motorola has the commitment to operate the system regardless of the number of users they have on it. we believe this will give them a huge incentive to make the network work really well because they're going to need to attract users to cover their cost. finally, devices. agencyless have to buy new devices, broadband enabled devices and there will be a cost for those devices as well. again, if an agency or jurisdiction chooses not to participate, they don't buy any new devices. so there's no cost there.

ok. finally, where are we? what happens next? we at the end stages of negotiating this boom agreement. we're down to just a handful of points that we're still negotiating. first thing has to happen and motorola and various jurisdictions, cities and counties in the bay area that own sites have to -- have to have agreements to allow motorola to use the sites and we're working on those agreements right now. second thing, the authority has to adopt a system funding plan and endorse the boom agreement. we're getting to, like i said, getting to the end of the negotiating of that agreement so the authority will have to endorse that agreement and it will go out to for member approval and each has the opportunity to approve or dace prove or recommend changes to the agreement. and finally the goal is to have all of the member agencies sign

on and have bay ricks actually execute a final boom agreement by december 6. i failed to mention the gran the -- grant that motorola has, has an aggressive time line. they're stimulus grants so the idea is get the money out there and get people hired and get jobs created sooner rather than later. so we are under a deadline to build the system and that is why we're working very hard to meet these deadlines and to fit the time line so that motorola can begin building the system and get it built within the very narrow time limits of the grant. well, that's it. i have said a lot of things. i would be happy to answer any questions you have about the system. i think you can tell i'm pretty excited about it. i have been working -- working almost exclusively on this project for the past few months.

i think it is a wonderful opportunity for san francisco and the bay area to adopt new technology that will have huge benefits for the folks that live here and visit here. i thank you. i will answer any questions that you may have. >> is this network dedicated -- a debt or -- is this a network a dedicated network to be used for emergencies or disaster declarations? and are the devices -- are they diagnostic in terms of what devices can be used? >> great question. first question -- who can use the network? congress has developed a fairly narrow definition of eligible users. an eligible user is public safety, first responder. it is not limited to a disaster

or a emergency incidents. law-enforcement officials, fire department, ems can use this on a daily basis. in addition to that, the fcc has taken action very recently to try to expand the definition of eligible user even more to governmental entities like transportation agencies and airport districts -- those types of entities that while not strictly public safety, served a fairly strong public safety function. we believe those entities could use it on a daily basis as well. obviously, in an emergency -- in an earthquake or a disaster -- everybody becomes an emergency services worker. when something big hits, obviously, i think any city employee would be eligible to use the system.

and we are actually working to expand the definition even more to allow public works -- there are a variety of functions that the city performs that i would consider public safety functions. we are just trying to expand the definition as broadly as possible. on the question of devices -- absolutely. both the arra and the fcc are setting specific standards and requirements for these networks. we are negotiating to make sure we have clear language in our agreement with motorola. motorola has to ensure that any device that is certified is compliant by the fcc or the national standards agency in washington will operate to it's full functionality on the

network. we believe that is a key component, to develop a key market for devices and hopefully drive down the price of those devices. do you have my contact information? i love to talk about this. if you have any questions that you would like to follow up, please do so anytime. then he gets very excited about this. thank you. -- >> he gets very excited about this. thank you. we are changing the way we have done disaster councils in the past when we go over reports, and we will provide executive summaries for you and begin looking at trends and the things we're learning. we thought that would be more helpful at that level for the council. i will turn it over to rob, who will give you that kind of overview, our deputy director. >> as she indicated, you have some executive summaries in the

packet. the one you have our are -- are bay to breaker, fallen hero and pride. what we're starting to look at -- a lot of times we go over very similar things from event to event. we're looking at trends, evolution, what we're learning. drawing from that, there is a list of all the points that you can read, and i am to have her -- i am happy to answer any questions. i am always available to you. in the last six or seven months, we have implemented webeoc. this was a long time in coming. those of you who have been here for a while know we had a platform to share information that was difficult to use. it was a very clunky program,

very difficult, and because we did not use it on a regular basis, that made it even worse. we went back to a paper-based system to look at how we do business as a city and how we want to operate in an emergency. we went to the vendors and said, "ok, here is how we work. give us a platform that works on the way we do things instead of a platform that causes us to have to change how we do things." long story, but in the end, we picked webeoc. it came out pretty strong, pretty easy to use. it is pretty intuitive. learning curves have to be accounted for, and each time we use it, we learn more and more. that goes to the more we use it, the better we get at it, and the more valuable it becomes, the more we can refine it appeared we have seen a trend where people are getting better at using it and we are identifying better how to use it.

utilization to coordinate events i think continues to be a good use of everybody's time. sometimes it seems a little slow. sometimes it seems like, "why are we here?" i would like to remind people that things do happen. while the reno air show is an anomaly, things do happen at these events. a grandstand collapse in indianapolis was something nobody ever thought of happening. whenever you have large crowds, things can happen. having a lot of people in the room to solve a problem right then is how to solve it. we look at how to do special event planning from a public safety perspective and making some changes to that. we are starting to look at a more holistic approach earlier out, getting all the disciplines together and refining how we will interact and communicate at any event, defining the parameters of the event, and looking at how we handle the issues that happen at events versus the larger 911 system.

the ultimate goal is that, particularly on the medical side, is that we do not impact the 911 system with a special event. if something happens like a grandstand collapse, all bets are off. but for normal things you should expect in a crowd of people, we should have those things covered and we should not have to reach into the 911 system. that creates a drain on the system and impacts everyone else in the system. that is our ultimate goal. we are getting closer to that as we continue to do this pre-event planning and look at our standards for events to have things in place ahead of time. one other thing i would say we really learned -- there is a comment in here about how we moved social media function into a more active part of the eoc. the bigger lesson is recognizing that we need to continue to focus on how we communicate with all of you, with our

constituency, and with the public in a timely, relevant basis. social media is one of those tools. that was a lesson that came out of the after action report. it speaks to a much bigger issue, which is always getting better about how we communicate across the board, both horizontal lee and vertically -- horizontal the -- horizontally and vertically. with that, if there are any questions you would like addressed, i will be happy to do so. >> questions? ok, thank you very much, rob. our next presentation this from our emergency services manager at the department of emergency services. >> i am going to tell you how grants have been going. like the federal government, we

have been suffering from the challenges of reduced budget. the two main grants we have coming -- there used to be 62 identified across the nation, which was reduced to 31. state homeland security, that was reduced by 32%. back at the federal level are starting to make their way towards us. i wanted to share with you where we are right now. with the 2008 grants, those are ones we are just closing now. 2009, we're starting to spend a lot more of those funds, as well as 2010. in both cases, the grant cycle is rather interesting. the grant will open, and we have almost a year's time from when we actually put the application in. it goes to the federal government. it is approved. it comes to us. it goes through a whole process.

in the print window, it is really the last 18 months we have to spend money -- in the three-year grant window, it is really the last 18 months we have to spend the money. the reason i want to call this account is when you see the numbers, you might be wondering when it -- why we are not spending the money now. it is just because of the nature of how grants go. some of the new things we have been doing is meeting with each of our different departments. we are starting to do a biannual grant review to let them know what projects have been awarded and how they are doing on spending. with different staffing changes, we want to make sure there is consistency among all the departments so they know what is being spent. something else we are doing -- in fact, we just concluded this -- is representatives from all the different departments have come to help us develop a scoring methodology we can use with new projects or proposals come forth. that way, we can use a consistent method of exploring all the different ones that are available and make sure we as a

grant team have guidance on how to match them up. if we turn to the second side of that page, it shows you in a graphical format where we stand. you will see we have almost $18 million over three different grant years and over a couple different grant streams that we currently have in the pipeline right now, but it needs a little bit of explanation. 2008, we close out. 2009, we are in the process of spending now. 2010, the monies that we have there, the large chunks and also in 2011, you will see those are almost $6,000,000.50 $0.5 million respectively -- for 2011, we have just put the application in -- almost $6 million and $5.5 million respectively. for 2011, we have just put the

application in. in 2010, we are in a process where we are starting to get things into the financial system. you can see what we have been awarded, what has been spent, what has been uncovered. what is still outstanding. then, we have some grass to kind of represent what is going on. >> why are we not spending any from 2009? is that just a function of the grant cycle? >> that is part of it. because the cycle is three years long, you want to spend as much as you can with whatever is currently active. we just finished up the 2008, so now, we're going to start going to 2009. >> [inaudible] >> competitiveness is based on when the grant closes, had we been able to expend the money in

a way that involves all the different guidelines. every grant has a three-year window. 2009 -- that is going to close next year in 2012. we have those three years, so we are in the process of getting in now and expending those moneys. >> other questions? all right, thank you. our next item is upcoming events. on the agenda, i said in a was going to present, but we will actually have three separate presenters because of the nature of the events. we have a lot of things happening, and i wanted to start with louis from the fleet week board. i thought you could give us an overview and let us know what to

expect. >> sure thing. thank you. if you guys ever wondered what happens when you become an ex- department head, you get volunteered for things. fleet week is a nonprofit organization that puts all the great events that the public sees, the parade of ships, the blue angels, welcoming the marines into san francisco, and san francisco is a fabulous host for those visitors. in 2010, i was asked to get involved because our honorary co-chair had come up with a great idea, which was -- dianne feinstein, by the way, is also an honorary co-chair. he had come up with the idea that if we have all these military folks in town, why not use that as an opportunity to do

some cross training between military and civilian assets relative to disaster response and the whole disaster response community? there are things like language is different. we set out in 2010 to have a whole program on board the big debt helicopter carrier with the hyper propulsion system, the greatest ship in the navy, the helicopter landing ship. on the hangar deck, we had a senior leader seminar in which we went through what is affectionately known -- everything has an acronym in the military, i have learned -- as defense support for civilian authorities, dsca. it said the foundation for going forward to have a robust training program that allows the bay area first responders to understand the military and vice versa. we had various briefings on the roles of local,